Command issuing apparatus for high-speed serial interface

ABSTRACT

In order to reduce load placed on a CPU (central processing unit) in providing SBP-2 (serial bus protocol 2) initiator capability, provided are a sequence control circuit activated by the CPU for controlling a command issue sequence, a packet processing circuit for assembling operation request blocks (ORB) into a transmission packet and extracting a status from a received packet; buffer for storing a command ORB provided by the CPU; a buffer for storing a management ORB provided by the CPU; a buffer for storing a status received for an issued management ORB and providing the status to the CPU; and a buffer for command for storing a status received for an issued command ORB and providing the status to the CPU.

BACKGROUND OF THE INVENTION

[0001] The present invention relates to a command issuing apparatus for a high-speed serial interface.

[0002] In recent years, IEEE 1394 interfaces have received attention as high-speed serial interfaces for interconnecting audiovisual apparatuses and computers. The IEEE 1394 technology can be used not only for communications between computers through ATAPI (AT Attachment Packet Interface) and SCSI (Small Computer System Interface), which are conventional parallel interfaces, but also for communications between audiovisual apparatuses. This is because IEEE 1394 defines asynchronous communication and isochronous communication.

[0003] When computer data is stored in a magnetic disk such as a hard disk or an optical disk such as a DVD-RAM or computer data stored in such a disk is read by a host computer using the IEEE 1394 technology, a control command and data is typically transmitted using asynchronous communication. SBP-2 (Serial Bus Protocol 2), which is a protocol using asynchronous communication, has been generally used for communication between the host computer (initiator) and the hard disk or DVD-RAM (target).

[0004] With the commencement of digital broad casting services in Japan, the fusion of audiovisual apparatuses and computers has been accelerated and a hard disk and DVD-RAM have begun to be used as a recording medium for a set top box (STB). Audiovisual data is recorded on these disks in a format that can be handled as a computer file in order to facilitate the management and editing of the data. In such a case, it is required that an SBP-2 initiator capability be provided in the STB, which is an audiovisual apparatus.

[0005] Because the dominating apparatuses having the SBP-2 initiator capability have been computers, central processing units (CPUs) offering sufficient speed performance have controlled the transmission and reception of all packets, especially the generation of packets containing operation request blocks (ORBs), in accordance with a program. However, in terms of a cost/performance ratio it is difficult to include a CPU offering sufficient speed performance in an audiovisual apparatus.

[0006] In addition, when audiovisual data is recorded or images are reproduced or edited in a target apparatus (such as a hard disk drive or DVD-RAM drive) by an initiator apparatus (STB), the CPU cannot provide sufficient command execution speeds and therefore transmission performance of the target apparatus cannot be fully exploited. Furthermore, required transfer performance of the entire system cannot be achieved.

SUMMARY OF THE INVENTION

[0007] It is an object of the present invention to reduce load on a CPU when it issues a command in an apparatus providing high-speed serial interface initiator capability.

[0008] To achieve the object, the present invention provides a command issuing apparatus as an initiator in a high-speed serial interface that issues a command to a target by using a packet, comprising: a sequence control circuit activated by a central processing unit (CPU) for controlling a command issue sequence; a packet processing circuit for assembling operation request blocks (ORB) to be issued into a transmission packet and extracting a status from a received packet; a command ORB transmission buffer for storing a command ORB provided by the CPU; a management ORB transmission buffer for storing a management ORB provided by the CPU; a status reception buffer for management for storing a status received for an issued management ORB and providing the status to the CPU; and a status reception buffer for command for storing a status received for an issued command ORB and providing the status to the CPU.

[0009] According to the present invention, once the CPU stores a command ORB or a management ORB in its transfer buffer and activates the sequence control circuit, no additional load is placed on the CPU until it receives a status for the ORB issued.

[0010] According to the present invention, an initiator capability with high response performance can be provided in the command issuing apparatus by using non-programmed control.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011]FIG. 1A shows a structure of a BWRQ packet on an IEEE 1394 bus.

[0012]FIG. 1B shows a structure of a QWRQ packet on the IEEE 1394 bus.

[0013]FIG. 1C shows a structure of a WRS packet on the IEEE 1394 bus.

[0014]FIG. 1D shows a structure of a BRRQ packet on the IEEE 1394 bus.

[0015]FIG. 1E shows a structure of a BRRS packet on the IEEE 1394 bus.

[0016]FIG. 2 shows a data format of a management ORB in SBP-2.

[0017]FIG. 3 shows a data format of a command ORB in SBP-2.

[0018]FIG. 4 shows a data format of a status in SBP-2.

[0019]FIG. 5 shows a diagram for explaining links between command ORBs in SBP-2.

[0020]FIG. 6 shows a state transition diagram of a target in SBP-2.

[0021]FIG. 7 shows a block diagram of a data transmission system in which an SBP-2 command issuing apparatus according to the present invention is provided.

[0022]FIG. 8 shows a sequence for issuing a management ORB by the command issuing apparatus shown in FIG. 7.

[0023]FIG. 9A shows a timing chart indicating operations of components shown in FIG. 7 when the management ORB is issued.

[0024]FIG. 9B shows a timing chart continued from FIG. 9A.

[0025]FIG. 10 shows a command ORB issue sequence performed by the command issuing apparatus shown in FIG. 7.

[0026]FIG. 11A shows a timing chart indicating operations of the components shown in FIG. 7 when a command ORB is issued.

[0027]FIG. 11B shows a timing chart continued from FIG. 11A.

[0028]FIG. 12A shows a sequence for issuing linked command ORBs performed by the command issuing apparatus shown in FIG. 7.

[0029]FIG. 12B shows a sequence diagram continued from FIG. 12A.

[0030]FIG. 13A shows a timing chart indicating operations of the components shown in FIG. 7 when the linked command ORBs are issued.

[0031]FIG. 13B shows a timing chart continued from FIG. 13A.

[0032]FIG. 13C shows a timing chart continued from FIG. 13B.

[0033]FIG. 14A shows a sequence for issuing an additional command ORB by the command issuing apparatus shown in FIG. 7 during the execution of linked command ORBs.

[0034]FIG. 14B shows a sequence continued from FIG. 14A.

[0035]FIG. 15A shows a timing chart indicating operations of the components shown in FIG. 7 when the additional command ORB is issued during the execution of the linked command ORBs.

[0036]FIG. 15B shows a timing chart continued from FIG. 15A.

[0037]FIG. 15C shows a timing chart continued from FIG. 15B.

[0038]FIG. 15D shows a timing chart continued from FIG. 15C.

[0039]FIG. 16 shows an operation sequence performed in the command issuing apparatus shown in FIG. 7 if command error occurs.

[0040]FIG. 17A shows a timing chart of the components shown in FIG. 7 when the command error occurs.

[0041]FIG. 17B shows a timing chart continued from FIG. 17A.

DETAILED DESCRIPTION OF THE INVENTION

[0042] Embodiments of the present invention will be described below in detail with reference to the accompanying drawings. However, the following description does not limit the technical scope of the present invention.

[0043]FIGS. 1A through 1E show structures of some of the asynchronous packets defined in IEEE 1394. IEEE 1394 defines request packets for requesting operations and response packets for returning the results of the operation requested with the request packets. When one of these packets is received, an acknowledge (ACK) packet indicating the state of the reception of the packet is returned to the requesting device. The ACK packet indicates a state such as “ack_complete”, which indicates the completion of an operation, “ack_pending”, which indicates that a request has been received and a requested operation is being processed, and “ack_busy”, which indicates a retransmission request (ack_busy). A request packet and a response packet are usually used in pairs.

[0044]FIGS. 1A, 1B, and 1D show request packets, a BWRQ packet (write request for data block packet), QWRQ packet (write request for data quadlet packet), and BRRQ packet (read request for data block packet), respectively. A WRS packet (write response packet) shown in FIG. 1C is defined for the write request (BWRQ and QWRQ) packets. A BRRS packet (read response for data block packet) shown in FIG. 1E is defined for the BRRQ packet. Each of these request and response packets contains a transaction code (tcode) identifying the type of packet and a transaction label (tl), which is tag information specific to a transaction. The response packets contain a response code (rcode) indicating a state of response. Thus, the type of transaction can be identified by tcode and a pair of request packet and response packet can be identified by tl. See the IEEE 1394-1995 standard for further information.

[0045]FIGS. 2, 3, and 4 show data formats specified in SBP-2. An initiator generates an ORB in its system memory. SBP-2 defines management commands for managing connections between the initiator and a target and command execution. These commands are included in a management ORB shown in FIG. 2 to handle them. Commands such as a READ command and WRITE command are included in a command ORB shown in FIG. 3 to handle them. A command is contained in a command_block field. FIG. 4 shows the data format of a status. Registers such as a MANAGEMENT_AGENT register and CommandAgent register are defined in a CSR (control and status register) space in the target. The CommandAgent register consists of AGENT_STATE, AGENT_RESET, ORB_POINTER, and DOORBELL registers.

[0046]FIG. 5 shows links between command ORBs. The next_ORB field, shown in FIG. 3, of a command ORB that is linked to no command ORB is set to Null. In particular, “1” in the start bit of next_ORB field indicates Null. On the other hand, if command ORB A is linked to command B, the next_ORB field of command A issued before the command ORB contains the address of command B, as shown in the upper section of FIG. 5. This allows the target to obtain a command ORB at an address indicated by the next_ORB field until the next_ORB field of an ORB command obtained indicates Null.

[0047] State management performed by a target in SBP-2 will be described below with reference to FIG. 6. As shown in FIG. 6, the target is managed with RESET, ACTIVE, SUSPEND, and DEAD states. These four states are indicated by an AGENT_STATE register, which is one of CommandAgent registers. The target is in the RESET state during power-up. When the ORB-POINTER register in the target is accessed and a command ORB is obtained, the target enters the ACTIVE state. After the completion of the command ORB, it returns a status and makes transition to the SUSPEND state. Subsequently, when the ORB_POINTER register or DOORBELL register is accessed and a command ORB is obtained, the target makes transition to the ACTIVE state and, after returning a status, enters the SUSPEND state. This sequence is repeated. If a command ORB abnormally ends or a transaction error occurs in the execution sequence of the command ORB, the target enters the DEAD state. Because the target in the DEAD state cannot continue to obtain command ORBs, the target causes the initiator to access the AGENT_RESET register to return to the RESET state.

[0048]FIG. 7 shows a block diagram of a data transmission system in which a SBP-2 command issuing apparatus according to the present invention is provided. In the system shown in FIG. 7, an initiator 1 is connected to a target 2 over an IEEE 1394 bus 3. The initiator 1 may be an STB and the target 2 may be a hard disk drive or optical disk drive, for example. The initiator 1 includes a CPU 10 and the command issuing apparatus 20. The command issuing apparatus 20 comprises a physical-layer controller (PHY) 21, a link-layer controller (LINK) 22, an asynchronous transmission FIFO buffer (ATF) 23, an asynchronous reception FIFO buffer (ARF) 24, a control register module 25, a transmission filter (TFIL) 26, a reception filter (RFIL) 27, a packet processing circuit (PPRC) 28, a sequence control circuit (SQC) 29, a command ORB transmission buffer (COTB) 30, a management ORB transmission buffer (MOTB) 31, a status reception buffer for management (SRBM) 32, and a status reception buffer for command (SRBC) 33.

[0049] The physical-layer controller 21 has the capabilities of initializing the bus 3, encoding/decoding data, performing arbitration, and providing/detecting a bias voltage. The link-layer controller 22 has the capabilities of sending and receiving packets and generating/detecting an error correcting code. The asynchronous transmission FIFO buffer 23 stores a packet to be transmitted and the asynchronous reception FIFO buffer 24 stores a received packet directed to the CPU 10. The control register module 25 is a group of registers used in various control operations performed by the CPU 10 in transmitting or receiving a packet, performing initial setting for issuing a command, storing an ORB, and reading a status.

[0050] The transmission filter 26 receives a packet transmission request from the packet processing circuit 28 or a packet transmission request from the CPU 10 and, if the transmission buffer 23 is empty, writes the requested packet into the transmission buffer 23. The transmission filter 26 has an arbitration function for giving priority to one of packet transmission requests provided from the packet processing circuit 28 and a packet transmission request from the CPU 10 at the same time. It also has the function of prohibiting a packet from being written into the transmission buffer 23 if it is not empty.

[0051] The reception filter 27 discriminates between a packet directed to the packet processing circuit 28 and a packet directed to the CPU 10. In particular, the reception filter 27 determines a packet as one directed to the packet processing circuit 28 based on information provided from the packet processing circuit 28 when a command is issued, that is, tcode and destination offset (packet destination address) for a request packet or tcode and tl for a response packet, and passes the received packet to the packet processing circuit 28. The reception filter 27 determines other received packets as ones directed to the CPU 10 and stores them in the reception buffer 24.

[0052] The packet processing circuit 28 generates packets and manages transactions related to a command issue sequence and the reception of a status. Details of its operation will be described later.

[0053] The sequence control circuit 29 controls a command issue sequence in cooperation with the command ORB transmission buffer 30 and management ORB transmission buffer 31. The sequence control circuit 29 receives from the CPU 10 or other blocks a request for accessing each of a MANAGEMENT_AGENT register and a CommandAgent register based on the address of each of the MANAGEMENT_AGENT register and CommandAgent register of the target 2 and the destination ID of the target 2 received from the CPU 10 through a control register module 25, generates a request packet, and provides it to the packet processing circuit 28. The sequence control circuit 29 also receives notification of the reception of a response packet responding to that request packet from the packet processing circuit 28 to manage the command issue sequence.

[0054] The command ORB transmission buffer 30 stores a command ORB provided by the CPU 10 through the control register module 25. In addition, the command ORB transmission buffer 30 has the function of automatically managing the addresses of command ORBs. In particular, when a command ORB is stored by the CPU 10, the command ORB transmission buffer 30 automatically decides the address of the command ORB and communicates the address to the sequence control circuit 29. The sequence control circuit 29 will use a BWRQ packet to write the address of the command ORB in the ORB_POINTER register of the target 2 when issuing the command ORB. The address of the command ORB is also communicated from the sequence control circuit 29 to the reception filter 27 through the packet processing circuit 28. If the destination_offset of the BWRQ packet received from the target 2 matches the address of the command ORB, the BWRQ packet is provided to the packet processing circuit 28 and the packet processing circuit 28 generates a BRRS packet containing an ORB read from the command ORB transmission buffer 30 and provides it to the transmission filter 26.

[0055] The command ORB transmission buffer 30 can store a plurality of ORBs. It has the capability of automatically performing ORB linking if an unissued command is in the command ORB transmission buffer 30 when a command ORB is provided from the CPU 10. As shown in the bottom section of FIG. 5, the command ORB transmission buffer 30 automatically assigns an address to the additionally buffered command ORB and changes the next_ORB field of the command ORB previously buffered to the address of the additionally buffered command ORB. The command ORB transmission buffer 30 also submits a request to the sequence control circuit 29 for access to the DOORBELL register of the target 2.

[0056] The management ORB transmission buffer 31 stores a management ORB provided by the CPU 10 through the control register module 25. In addition, the management ORB transmission buffer 31 has the capability of automatically managing addresses of management ORBs. In particular, when a management ORB is buffered by the CPU 10, the management ORB transmission buffer 31 automatically decides the address of the management ORB and communicates the address to the sequence control circuit 29. The sequence control circuit 29 will use a BWRQ packet to write the address of the ORB into the MANAGEMENT_AGENT register of the target 2 when issuing the management ORB. The address of the management ORB is also communicated from the sequence control circuit 29 to the reception filter 27 through the packet processing circuit 28. If the destination_offset of a BWRQ packet received from the target 2 matches the address of the management ORB, the BWRQ packet is provided to the packet processing circuit 28. The packet processing circuit 28 generates a BRRS packet containing an ORB read from the management ORB transmission buffer 31 and provides it to the transmission filter 26.

[0057] The status reception buffer for management 32 stores a status received for an issued management ORB and communicates it to the CPU 10. When the reception filter 27 receives from the target 2 a BWRQ packet having a destination_offset that matches the address in STATUS_FIFO provided from the CPU 10 to the reception register 27 through the control register module 25 before the issue of the management ORB, the reception filter 27 provides the BWRQ packet to the packet processing circuit 28. If the address of the management ORB communicated from the management ORB transmission buffer 31 matches the ORB_offset_hi/ORB_offset_lo (see FIG. 4) of the received status, the packet processing circuit 28 provides the status to the status reception buffer for management 32.

[0058] The status reception buffer for command 33 stores a status received for an issued command ORB and communicates it to the CPU 10. When the reception filter receives a BWRQ packet having a destination_offset that matches the address in STATUS_FIFO communicated from the CPU 10 to the reception filter 27 through the control register module 25 from the target 2 before the issue of the command ORB, the reception filter 27 provides the BWRQ packet to the packet processing circuit 28. If the address of the management ORB communicated from the management ORB transmission buffer 31 does not matches the ORB_offset_hi/ORB_offset_lo of the received status, the packet processing circuit 28 provides the status to the status reception buffer for command 33. The status reception buffer for command 33 can store a plurality of statuses. The status reception buffer for command 33 also has the function of submitting a request to the sequence control circuit 29 for access to the AGENT_RESET register of the target 2, if it detects that the status it received is an error (bit d set in the status shown in FIG. 4 indicates that the relevant command ORB is in error).

[0059] Five exemplary operations of the command issuing apparatus 20 shown in FIG. 1 will be described below.

[0060] (First Exemplary Operation)

[0061] An operation of the command issuing apparatus 20 that is performed when a management ORB is issued will be describe with reference to FIGS. 8, 9A, and 9B. While an initiator 1 should obtain the address of a MANAGEMENT_AGENT register from configuration ROM of a target 2 before it issues the management ORB, the description of that operation will be omitted here.

[0062] (1) The CPU 10 sets the address of the MANAGEMENT_AGENT register obtained form the target 2 and the node ID of the target 2 in the sequence control circuit 29 and sets the address of a status reception buffer (STATUS_FIFO) in the status reception buffer for management 32 as initial settings.

[0063] (2) The CPU 10 generates a management ORB to be issued and stores it in the management ORB transmission buffer 31. The management ORB transmission buffer 31 decides the address (*P in FIG. 8) of the management ORB and communicates it to the sequence control circuit 29. It also communicates the address to the packet communication circuit 28 and reception filter 27.

[0064] (3) The CPU 10 requests the sequence control circuit 29 to issue the management ORB (phase “a” in FIG. 8 starts).

[0065] (4) The sequence control circuit 29 generates a BWRQ packet shown in FIG. 1A in which the node ID of the target 2 provided from the CPU 10 is set in destination_ID, the address of the MANAGEMENT_AGENT register is set in destination_offset, the address (*P) of the management ORB provided from the management ORB transmission buffer 31 is set in data_field, and tcode is set to “1” (indicating that this is a BWRQ packet), and data_length is set to “8”. Then the sequence control circuit 29 provides it to the packet processing circuit 28.

[0066] (5) The packet processing circuit 28 sets a given value in tl in the BWRQ packet and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21. The packet processing circuit 28 communicates tcode and tl to the reception filter 27.

[0067] (6) The target 2 receives the BWRQ packet and returns a WRS packet.

[0068] (7) When the reception filter 27 determines that tcode of the received WRS packet is WRS and tl matches one provided from the packet processing circuit 28, the reception filter 27 notifies the packet processing circuit 28 and sequence control circuit 29 of the reception of the WRS packet and discards the WRS packet itself (phase “a” in FIG. 8 ends).

[0069] (8) Then, the target 2 sends a BRRQ packet to the address (*P) of the management ORB in order to obtain the management ORB. If the reception filter 27 determines that destination_offset of the received BRRQ packet matches the address (*P) of the management ORB communicated from the packet processing circuit 28, then it notifies the packet processing circuit 28 of the reception of the BRRQ packet, provides tl to it, and discards the BRRQ packet itself (phase “b” in FIG. 8 starts).

[0070] (9) The packet processing circuit 28 places the management ORB read from the management ORB transmission buffer 31 in data_field to generate a BRRS packet. Then, the packet processing circuit 28 changes tl of the BRRS packet to tl received from the reception filter 27 and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21.

[0071] (10) The target 2 receives the BRRS packet to obtain the management ORB and executes it (phase “b” in FIG. 8 ends).

[0072] (11) After the completion of the ORB, the target 2 generates a status shown in FIG. 4, places it in data_field in a BWRQ packet, and sends it to the initiator 1 (phase c in FIG. 8 starts).

[0073] (12) If the reception filter 27 determines that destination_offset in the BWRQ packet containing the received status matches the address in STATUS_FIFO set in the CPU 10, it notifies the packet processing circuit 28 of the reception of the BWRQ packet and provides the BWRQ packet to the packet processing circuit 28.

[0074] (13) The packet processing circuit 28 references ORB_offset_hi and ORB_offset_lo (see FIG. 4) in the status contained in data_field in the BWRQ packet and, if they matches the address (*P) of the management ORB received from the management ORB transmission buffer 31, stores the status in the status reception buffer for management 32. At the same time, it generates a WRS packet for the BWRQ packet and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21.

[0075] (14) When the packet processing circuit 28 determines that information in an ACK packet for the transmitted WRS packet indicates a normal end, it notifies the CPU 10 of the reception of the status for the management ORB (phase “c” in FIG. 8 ends).

[0076] (15) The CPU 10 reads the status from the status reception buffer for management 32.

[0077] As described above, the command issuing apparatus 20 can eliminate load which would be placed on the CPU 10 until the CPU 10 receives the notification of the reception of the status and reads the status once the CPU 10 performs the initial setting, generates and registers a management ORB, and requests the issue of the management ORB.

[0078] (Second Exemplary Operation)

[0079] An operation of the command issuing apparatus 20 when issuing a command ORB will be described below with reference to FIGS. 10, 11A, and 11B. While an initiator 1 should obtain the address of a CommandAgent register, which can be obtained by logging into a target 2, before issuing a command ORB, the description of that operation will be omitted herein.

[0080] (1) The CPU 10 sets the address of the CommandAgent register obtained from the target 2 and the node ID of the target 2 in the sequence control circuit 29 and sets the address of a status reception buffer (STATUS_FIFO) in the status reception buffer for command 33 as initial settings. The node ID of the target 2 is the same as the value used in issuing a management ORB. Therefore, if the management ORB has been previously issued, setting of the node ID may be omitted. If the command ORB is issued a second or subsequent time, setting of the addresses of the CommandAgent register and STATUS_FIFO also may be omitted.

[0081] (2) The CPU 10 generates the command ORB to be issued and stores it in the command ORB transmission buffer 30. The command ORB transmission buffer 30 decides the address (*P in FIG. 10) of the command ORB and communicates it to the sequence control circuit 29. It also communicates the address to the packet processing circuit 28 and the reception filter 27.

[0082] (3) The CPU 10 requests the sequence control circuit 29 to issue the command ORB (phase “a” in FIG. 10 starts).

[0083] (4) The sequence control circuit 29 generates a BWRQ packet shown in FIG. 1A in which the node ID of the target 2 provided from the CPU 10 is set in destination_ID, the address of an ORB_POINTER register is set in destination_offset, the address (*P) of the command ORB provided from the command ORB transmission buffer 30 is set in data_field, tcode is set to “1” (indicating that this is a BWRQ packet), and data_length is set to “8”. Then the sequence control circuit 29 provides the BWRQ packet to the packet processing circuit 28.

[0084] (5) The packet processing circuit 28 sets a given value in tl in the BWRQ packet and sends out the BWRQ packet onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21. The packet processing circuit 28 communicates tcode and tl to the reception filter 27.

[0085] (6) The target 2 receives the BWRQ packet and returns a WRS packet.

[0086] (7) If the reception filter 27 determines that tcode in the WRS packet it received is WRS and that tl matches the one provided from the packet processing circuit 28, then it notifies the packet processing circuit 28 and the sequence control circuit 29 of the reception of the WRS packet and discards the WRS packet itself (phase “a” in FIG. 10 ends).

[0087] (8) Then, the target 2 sends a BRRQ packet to the address (*P) of the command ORB in order to obtain the command ORB. If the reception filter 27 determines that destination_offset of the received BRRQ packet matches the address (*P) of the command ORB communicated from the packet processing circuit 28, then it communicates the reception of the BRRQ packet and tl to the packet processing circuit 28 and discards the BRRQ packet itself (phase “b” in FIG. 10 starts).

[0088] (9) The packet processing circuit 28 reads the command ORB from the command ORB transmission buffer 30 and places it in data_field to generate a BRRS packet. Then, the packet processing circuit 28 changes tl of the BRRS packet to tl received from the reception filter 27 and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21.

[0089] (10) The target 2 receives the BRRS packet to obtain the command ORB and executes it (phase “b” in FIG. 10 ends).

[0090] (11) After the completion of the execution of the ORB, the target 2 generates a status shown in FIG. 4, places it in data_field in the BWRQ packet, and sends it to the initiator 1 (phase “c” in FIG. 10 starts).

[0091] (12) If the reception filter 27 determines that the destination_offset in the BWRQ packet containing the status matches the address in the STATUS_FIFO set in the CPU 10, then it notifies the packet processing circuit 28 of the reception of the BWRQ packet and provides the BWRQ packet to the packet processing circuit 28.

[0092] (13) The packet processing circuit 28 references ORB_offset_hi and ORB_offset_lo (see FIG. 4) in the status contained in data_field in the BWRQ packet and, if they do not mach the address of the management ORB received from the management ORB transmission buffer 31, stores the status in the status reception buffer for command 33. At the same time, it generates a WRS packet for the BWRQ packet and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical layer controller 21.

[0093] (14) If the packet processing circuit 28 determines that information in an ACK packet for the transmitted WRS packet indicates a normal end, then it notifies the CPU 10 of the reception of the status for the command ORB (phase “c” in FIG. 10 ends).

[0094] (15) The CPU 10 reads the status from the status reception buffer for command 33.

[0095] Thus, the command issuing apparatus 20 can eliminates the load which would be placed on the CPU 10 during the period until it receives the notification of the reception of the status and reads the status after it performs the initial setting, generates and stores a command ORB, and requests the issue of the command ORB. While operation for issuing the command ORB through access to the ORB_POINTER register has been described with respect to the exemplary operation, similar functions are performed in issuing a command ORB through access to the DOORBELL register while AGENT_STATE is SUSPEND.

[0096] (Third Exemplary Operation)

[0097] An operation of the command issuing apparatus 20 when issuing linked command ORBs will be described below with reference to FIGS. 12A-12B and 13A-13C. In this example, an operation before the command C in FIG. 5 is added, that is, an operation for issuing two command ORBs of command A and command B, will be described.

[0098] In this exemplary operation, the CPU 10 generates two command ORBs (ORB A, ORB B) to be issued and stores them in the command ORB transmission buffer 30 in sequence. The command ORB transmission buffer 30 decides the address of the ORB of command A (“*A” in FIG. 12A) and communicates it to the sequence control circuit 29. It also communicates the address to the packet processing circuit 28 and the reception filter 27. Then, the command ORB transmission buffer 30 decides the address of the ORB of command B (“*B” in FIG. 12A) and changes the next_ORB field of the ORB of command A to “*B”. As with the ORB of command A, it communicates the address (“*B” in FIG. 12A) of the ORB of command B to the packet processing circuit 28 and the reception filter 27.

[0099] The process from phase “a” to phase “c” in FIG. 12A proceeds as in the second exemplary operation. When the CPU 10 is notified of the reception of status for the ORB of command A, the CPU 10 reads the status from the status reception buffer for command 33. Alternatively, a plurality of statuses may be stored at a time in the status reception buffer for command 33, thereby allowing the read of the status for the ORB of command A by the CPU 10 to be postponed until a status for the ORB of command B is read.

[0100] The target 2 determines that the next_ORB field in the ORB of command A is not Null but *B. Thus, the ORB of command B is obtained and the execution of it is started. Phases d and e in FIG. 12B are the same as phases b and c in FIG. 12A.

[0101] As described above, the command issuing apparatus 20 allows the CPU 10 to buffer a plurality of command ORBs with leaving their next_ORB field Null rather than intentionally linking the ORBs when the CPU 10 issues the command ORBs, thereby reducing the load on the CPU 10.

[0102] (Fourth Exemplary Operation)

[0103] An operation of the command issuing apparatus 20 when an additional command ORB is issued during the execution of a linked command ORB will be described below with reference to FIGS. 14A-14B and 15A-15D. In this example, an operation for an additional command C is issued during the execution of command A after two ORBs for commands A and B are linked and issued as shown in FIG. 5.

[0104] Phases a and b in FIG. 14A proceed as those in the third exemplary operation. The CPU 10 generates the ORB of the third command, C, and stores it in the command ORB transmission buffer 30 during the execution of the ORB of command A. The command ORB transmission buffer 30 decides the address (*C in FIG. 14A) of the ORB of command C and communicates it to the packet processing circuit 28 and the reception filter 27. The command ORB transmission buffer 30 changes the next_ORB field of the ORB of command B buffered previously to “*C” and requests the sequence control circuit 29 to access the DOORBELL register of the target 2. The sequence control circuit 29 does not access the DOORBELL register because the ORB of command A is being executed. However, if the last ORB linked, the ORB of command B, is being executed, it accesses the DOORBELL register.

[0105] The description of phase c in FIG. 14A and phases d through g in FIG. 14B would not be needed. Also in this example, a plurality of statuses may be stored at a time in the status reception buffer for command 33 so that the read of the status for the ORBs of commands A and B by the CPU 10 can be postponed until a status for the ORB of command C is read.

[0106] In this way, the command issuing apparatus 20 allows, when the CPU 10 issues an additional command ORB during the execution of a plurality of linked command ORBs issued, the CPU 10 to buffer all the command ORBs with leaving their next_ORB field Null rather than intentionally linking the ORBs, thereby reducing the load on the CPU 10.

[0107] (Fifth Exemplary Operation)

[0108] An operation of the command issuing apparatus 20 in a case where a command error occurs will be described below with reference to FIGS. 16 and 17A-17B. Transition to the DEAD state and a return to the RESET state will be described herein.

[0109] Phases a and b in FIG. 16 proceed as in the second exemplary operation. After the target 2 returns a WRS packet to the initiator 1 in phase “a” in FIG. 16, it makes transition from the RESET state to the ACTIVE state. If an error occurs while the target 2 is executing an ORB, the target 2 generates an error status according to the format shown in FIG. 4, places it in data_field in a BWRQ packet, and sends it to the initiator 1. The error status is generated by setting bit “d” in FIG. 4. Then, the target 2 enters the DEAD state (phase “c” in FIG. 16 starts).

[0110] Phases c and d in FIG. 16 will be detailed below.

[0111] (1) If the reception filter 27 determines that destination_offset in the BWRQ packet containing the received error status matches the address in STATUS_FIFO set in the CPU 10, then it notifies the packet processing circuit 28 of the reception of the BWRQ packet and provides the BWRQ packet to the packet processing circuit 28.

[0112] (2) The packet processing circuit 28 references ORB_offset_hi and ORB_offset_lo in the status (see FIG. 4) contained in the data_field in the BWRQ packet and, if they do not match the address of a management ORB received from the management ORB transmission buffer 31, stored the status in the status reception buffer for command 33. At the same time, it generates a WRS packet for the BWRQ packet and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21.

[0113] (3) If the packet processing circuit 28 determines that information in an ACK packet responding to the sent WRS packet indicates that a successful termination, it notifies the CPU 10 of the reception of the status for the command ORB (phase “c” in FIG. 16 ends).

[0114] (4) If the status reception buffer for command 33 storing the status determines that bit “d” in the status shown in FIG. 4 is set, it requests the sequence control circuit 29 to access the AGENT_RESET register of the target 2.

[0115] (5) The CPU 10 reads the status from the status reception buffer for command 33.

[0116] (6) When the sequence control circuit 29 receives the request to access the AGENT_RESET register, it generates a QWRQ packet shown in FIG. 1B in which the node ID of the target 2 provided by the CPU 10 is set in destination_ID, the address in the AGENT_RESET register is set in destination_offset, a given value is set in quadlet_data, and tcode is set to “0”, then provides the QWRQ packet to the packet processing circuit 28 (phase “d” in FIG. 16 starts).

[0117] (7) The packet processing circuit 28 sets a given value in tl in the QWRQ packet and sends out it onto the 1394 bus 3 through the transmission filter 26, transmission buffer 23, link-layer controller 22, and physical-layer controller 21. The packet processing circuit 28 communicates the tcode and tl to the reception filter 27.

[0118] (8) The target 2 receives the QWRQ packet and returns a WRS packet. Then the target 2 enters the RESET state.

[0119] (9) If the reception filter 27 determines that tcode in the received WRS packet is WRS and tl matches one provided from the packet processing circuit 28, it notifies the packet processing circuit 28 and the sequence control circuit 29 of the reception of the WRS packet and discard the WRS packet itself (phase “d” in FIG. 16 ends).

[0120] (10) The sequence control circuit 29 notifies the CPU 10 of the access to the AGENT_RESET register.

[0121] As described above, the command issuing apparatus 20 eliminates the need for the CPU 10 to perform the action of changing the target 2 to the RESET state even if the target 2 makes transition to the DEAD state because of an abnormal end of an issued command ORB, thereby reducing the load on the CPU 10. In addition, if an error occurs while linked command ORBs are being executed, the command issuing apparatus 20 can continue to issue stored command ORBs by accessing the ORB_POINTER register once it accesses the AGENT_RESET register, therefore the CPU 10 can continue issuing command ORBs. 

What is claimed is:
 1. A command issuing apparatus as an initiator in a high-speed serial interface for issuing a command to a target by using a packet, comprising: a sequence control circuit activated by a central processing unit (CPU) for controlling a command issue sequence; a packet processing circuit for assembling operation request blocks (ORB) to be issued into a transmission packet and extracting a status from a received packet; a command ORB transmission buffer for storing a command ORB provided by said CPU; a management ORB transmission buffer for storing a management ORB provided by said CPU; a status reception buffer for management for storing a status received for an issued management ORB and providing the status to said CPU; and a status reception buffer for command for storing a status received for an issued command ORB and providing the status to said CPU.
 2. The command issuing apparatus according to claim 1, further comprising: a transmission buffer for storing a packet to be transmitted to said target; a transmission filter for arbitrating between a packet transmission request from said packet processing circuit and a packet transmission request from said CPU and writing a packet to be sent into said transmission buffer; a reception buffer for storing a packet directed to said CPU; and a reception filter for classifies the received packet as a packet directed to said packet processing circuit or as a packet directed to said CPU according to the content of the received packet.
 3. The command issuing apparatus according to claim 1, wherein said sequence control circuit generates and issues a packet accessing a MANAGEMENT_AGENT register of said target based on a parameter provided by said CPU.
 4. The command issuing apparatus according to claim 1; wherein said sequence control circuit generates and issues a packet accessing an ORB_POINTER register of said target based on a parameter provided by said CPU.
 5. The command issuing apparatus according to claim 1, wherein said command ORB transmission buffer has a capacity for storing a plurality of command ORBs at a time.
 6. The command issuing apparatus according to claim 5, wherein said command ORB transmission buffer automatically assigns and rewrites an address into a next_ORB field so that a plurality of ORBs to be stored are linked even if the next_ORB field is null.
 7. The command issuing apparatus according to claim 5, wherein said command ORB transmission buffer rewrites the next_ORB field to link the ORBs, and then requests said sequence control circuit to access a DOORBELL register of said target when a new command ORB is stored during the execution of a command ORB; and said sequence control circuit generates and issues a packet accessing said DOORBELL register in response to the request from said command ORB transmission buffer.
 8. The command issuing apparatus according to claim 1, wherein said status reception buffer for command has a capacity for storing a plurality of statuses at a time.
 9. The command issuing apparatus according to claim 1, wherein said status reception buffer for command requests said sequence control circuit to access an AGENT_RESET register of said target if a received status is error status; and said sequence control circuit generates and issues a packet accessing said AGENT_RESET register in response to the request from said status reception buffer for command. 